home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group01b.txt
/
000158_icon-group-sender_Wed Oct 17 09:02:56 2001.msg
< prev
next >
Wrap
Internet Message Format
|
2002-01-03
|
3KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id f9HG1WI13928
for icon-group-addresses; Wed, 17 Oct 2001 09:01:32 -0700 (MST)
Message-Id: <200110171601.f9HG1WI13928@baskerville.CS.Arizona.EDU>
Date: Wed, 17 Oct 2001 14:25:05 +1300 (NZDT)
From: "Richard A. O'Keefe" <ok@atlas.otago.ac.nz>
To: icon-group@cs.arizona.edu, jsampson@indexes.u-net.com
Subject: Re: French colonic lavage revisited
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
Content-Length: 2008
"John Sampson" <jsampson@indexes.u-net.com> wrote:
Steve Wampler kindly helped me with the previous problem I had, but I am now
wondering if there is a DOS bug concerning this character. Or are there two
vertical stroke characters, one with a break in it and one without?
In ISO Latin 1, hence also in Windows CP 1252, there are indeed two
vertical stroke characters, one with a break in it (0xA6) and one
without (7C).
>From the Unicode 3.1.1 MAPPINGS collection:
ISO Latin 1:
0x7C 0x007C # VERTICAL LINE
0xA6 0x00A6 # BROKEN BAR
In the VENDORS/MICSFT/WINDOWS subcollection of MAPPINGS,
grep '^0XDD[ ]' * found
CP1250.TXT:0xDD 0x00DD #LATIN CAPITAL LETTER Y WITH ACUTE
CP1251.TXT:0xDD 0x042D #CYRILLIC CAPITAL LETTER E
CP1252.TXT:0xDD 0x00DD #LATIN CAPITAL LETTER Y WITH ACUTE
CP1253.TXT:0xDD 0x03AD #GREEK SMALL LETTER EPSILON WITH TONOS
CP1254.TXT:0xDD 0x0130 #LATIN CAPITAL LETTER I WITH DOT ABOVE
CP1255.TXT:0xDD #UNDEFINED
CP1256.TXT:0xDD 0x0641 #ARABIC LETTER FEH
CP1257.TXT:0xDD 0x017B #LATIN CAPITAL LETTER Z WITH DOT ABOVE
CP1258.TXT:0xDD 0x01AF #LATIN CAPITAL LETTER U WITH HORN
CP874.TXT:0xDD #UNDEFINED
CP932.TXT:0xDD 0xFF9D #HALFWIDTH KATAKANA LETTER N
CP936.TXT:0xDD #DBCS LEAD BYTE
CP949.TXT:0xDD #DBCS LEAD BYTE
CP950.TXT:0xDD #DBCS LEAD BYTE
and grep 'BROKEN BAR' * found
CP1250.TXT:0xA6 0x00A6 #BROKEN BAR
CP1251.TXT:0xA6 0x00A6 #BROKEN BAR
CP1252.TXT:0xA6 0x00A6 #BROKEN BAR
CP1253.TXT:0xA6 0x00A6 #BROKEN BAR
CP1254.TXT:0xA6 0x00A6 #BROKEN BAR
CP1255.TXT:0xA6 0x00A6 #BROKEN BAR
CP1256.TXT:0xA6 0x00A6 #BROKEN BAR
CP1257.TXT:0xA6 0x00A6 #BROKEN BAR
CP1258.TXT:0xA6 0x00A6 #BROKEN BAR
CP932.TXT:0xEEFA 0xFFE4 #FULLWIDTH BROKEN BAR
CP932.TXT:0xFA55 0xFFE4 #FULLWIDTH BROKEN BAR
CP936.TXT:0xA957 0xFFE4 #FULLWIDTH BROKEN BAR
There should not, therefore, be any disagreement about what 0xDD or 0xA6
or BROKEN BAR are in any of the CP125? Windows character sets.